Skip to content

Conversation

@Thunkar
Copy link
Contributor

@Thunkar Thunkar commented Jan 16, 2026

Allows ALL methods in the wallet to be batched (because why not). Initially I was going for allowing them on a case-by-case basis, but integrating the Wallet SDK has made apparent apps can have many interaction flows and this extra flexibility is nice.

Updated the migration notes and in the process realized I missed exporting some artifacts in #19457, so here they are (protocol contract wrappers)

@Thunkar Thunkar requested review from benesjan and nventuro January 16, 2026 06:57
@Thunkar Thunkar self-assigned this Jan 16, 2026
@Thunkar Thunkar requested a review from mverzilli January 16, 2026 06:57
Copy link
Contributor

@benesjan benesjan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

BTW I just merged my router contract renaming PR so you will need to update the exports here

/**
* Creates batch schemas from the individual wallet methods
* This allows us to define them once and derive batch schemas automatically,
* reducing duplication and ensuring consistency.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 120 chars are extra smol here 🧐

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't follow, this comment is 78 chars long at a max?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean that I would expect you to wrap at 120 but it's just a detail

Allows ALL methods in the wallet to be batched (because why not). Initially I was going for allowing them on a case-by-case basis, but integrating the Wallet SDK has made apparent apps can have many interaction flows and this extra flexibility is nice.

Updated the migration notes and in the process realized I missed exporting some artifacts in #19457, so here they are (protocol contract wrappers)

Co-authored-by: thunkar <[email protected]>
@AztecBot AztecBot force-pushed the gj/wallet_full_batchability branch from 4765c91 to aa3d3bd Compare January 18, 2026 18:11
@AztecBot AztecBot added this pull request to the merge queue Jan 19, 2026
@AztecBot
Copy link
Collaborator

AztecBot commented Jan 19, 2026

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/2d6f5f87781bbee7�2d6f5f87781bbee78;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_epochs/epochs_invalidate_block.parallel.test.ts "committee member invalidates a block if proposer does not come through" (94s) (code: 1) group:e2e-p2p-epoch-flakes (\033Aztec Bot\033: feat: wallet full batchability (#19652))

Merged via the queue into next with commit 1c4d3b1 Jan 19, 2026
17 checks passed
@AztecBot AztecBot deleted the gj/wallet_full_batchability branch January 19, 2026 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants